home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
bbs
/
nmfwd205.zip
/
WHATSNEW.TXT
< prev
Wrap
Text File
|
1996-06-18
|
29KB
|
754 lines
NmFwd
Changes and Additions
2.05 Public Release, June 18 1996
- Fixed problem with V7 semaphores that caused access
violation.
2.04 Very short lived, June 18 1996
- Robot answers are not forwarded to the specified list of
points when the applicable primary address is a point.
- OS/2: New option to configure the type of date
(Creation or LastWrite) to be used for deleting
old files in the temporary directory:
Tmp_Fa_Kill <days> [Creation|Write]
The default is Creation.
Example:
Tmp_Fa_Kill 10 Creation
- Semaphore implemented on V7 nodelist files,
as per FastLst specifications.
New errorlevel 11 on semaphore timeout.
- New Icon by Andrea Vavassori.
2.03 Public release, March 22 1996
- Multi-Line files.bbs descriptions are now
supported. To enable this feature the way you
like, please use the "MultiLineDesc <nnn>
[<c>]" statement, specifying the continuation
column and character.
For example, to have the 2nd and following
description lines in files.bbs preceded by
31 spaces, use:
MultiLineDesc 31
To have the continuation lines preceded by a
'|' character, use:
MultiLineDesc 29 |
- A multi-line description accounts for ONE line
in the file manager commands.
- New statement: UniqueDmpLine.
Makes NmFwd generate FILES.DMP filebase files with
descriptions on one line only (multiple lines are
concatenated).
By default, NmFwd outputs multi-line descriptions
without changes to FILES.DMP: when using
L)ocate and N)ewfiles commands, Maximus will
respect the original formatting, but the
continuation lines will be aligned to the left.
When this statement is used, the original
formatting of descriptions is lost (in the
filebase) but Maximus will be able to word-wrap
and align when executing L)ocate or N)ewfiles
commands.
- ListDate format (date and size of files
reported in files.bbs) and the various date
styles (Usa, Euro, Japan) are now supported.
- New -H "subject" switch for areafix, to get
help.
- New "AfHelpFile <filename>" statement for
specifying a help file for areafix.
- New %Query %List %Rescan %Help commands
available for the body of messages addressed to
areafix, with the same meaning of the
corresponding -q -l -r -h switches in the
subject.
- Now the areafix add command can optionally
include a '+' character; the following commands
are equivalent:
APWORKS
+APWORKS
- OS/2: Fixed problems with areafix rescans for
echotags containing special OS/2 characters
(e.g. the & command separator). When the
command interpreter must be loaded, the
parameters are passed between quotes.
2.02
- The default zone for messages read from *.MSG
netmail areas (not containing a ^AINTL kludge) is
now the zone of the primary address for THAT
netmail area.
Previously the (global) primary address was used
for zone assumptions in any netmail area.
2.01
- Areafix bugfix: when adding a node to an area
with NO links, a Carriage Return was erroneously
added between the area definition and the added
link.
This problem is not very likely to happen on
"normal" areas since at least the feed is usually
present.
Anyway it might create problems in the case of
"local" echomails that are created without any
link.
This is a very old bug that has unfortunately
not been reported until the release of v 2.00.
2.00
- Conversion of FileManager and UserManager to
Maximus 3.xx.
- WARNING: this version DOES NOT work with
Maximus 2.xx.
- WARNING: this version is NOT a drop-in
replacement for v. 1.90: you MUST read the
following points in this whatsnew and make the
required modifications in nmfwd.cfg.
- The "MaxPrm <filename>" statement MUST be moved
from the "FileManager" section to the "System"
one.
- If the "MAXIMUS" environment variable is
defined, the "MaxPrm <filename>" statement is
optional and works as an override.
- New errorlevel 9 for errors accessing the
Maximus PRM file (usually Max.Prm).
FileManager:
- New syntax for RFAccess and RFDefAccess:
RFAccess <pwd> <acs> [<points>]
RFDefAccess <acs> [<points>]
Where:
<pwd> is the password to be used (as the
subject of a netmail message) for accessing the
filemanager with <acs> privilege.
<acs> is a <level>[/<keys>] access string that
specifies the level and keys available to the
person who uses <pwd>. <level> can be any level
"name" defined in the Maximus Access.Ctl as
well as a level number.
<points> is a list of points that must receive
the answers of the FileManager.
E.g.
RFAccess SysOpPwd SysOp/U 0 2
Specifies that the password "SysOpPwd" grants
the "SysOp/U" access and the answers must be
written to the local netmail ('0') and sent to
point 2 ('2').
Please note that for security reasons the
answers are sent to <points> ONLY, even if the
original message was from another node.
RFDefAccess Normal 0
Specifies that people addressing the
FileManager with no valid password receive
"Normal" access and the answers must be written
to the local netmail (besides being sent to the
addressee).
- New syntax for all the statements that define
the access requirements for the FileManager
commands:
<command> <acs> [<areas>]
where:
<command> is the name of a FileManager comm